SherbyNet - /page/wikibook/entry.mu

Micron Document

<!DOCTYPE html>

<title>Query string</title>

</head>

Query string

</h1>

</header>

A query string is a part of a uniform resource locator (<a href="URL" title="URL">URL</a>) that assigns values to specified parameters. A query string commonly includes fields added to a base URL by a Web browser or other client application, for example as part of an HTML document, choosing the appearance of a page, or jumping to positions in multimedia content.

A web server can handle a <a href="HTTPS" title="HTTPS">Hypertext Transfer Protocol</a> (HTTP) request either by reading a file from its <a href="File_system" title="File system">file system</a> based on the <a href="URL" title="URL">URL</a> path or by handling the request using logic that is specific to the type of resource. In cases where special logic is invoked, the query string will be available to that logic for use in its processing, along with the path component of the URL.

<div class="mw-heading mw-heading2"><h2 id="Structure">Structure</h2></div>

A typical URL containing a query string is as follows:<style data-mw-deduplicate="TemplateStyles:r1244412712">

/* start https://en.wikipedia.org/ */

.mw-parser-output .templatequote{overflow:hidden;margin:1em 0;padding:0 32px}.mw-parser-output .templatequotecite{line-height:1.5em;text-align:left;margin-top:0}@media(min-width:500px){.mw-parser-output .templatequotecite{padding-left:1.6em}}

/* end https://en.wikipedia.org/ */

</style><blockquote class="templatequote"><code>https://example.com/over/there?name=ferret</code></blockquote>

When a server receives a request for such a page, it may run a program, passing the query string, which in this case is <code>name=ferret</code>, unchanged to the program. The question mark is used as a separator, and is not part of the query string.<a href="#cite_note-1">[1]</a><a href="#cite_note-2">[2]</a>

<a href="Web_Framework" class="mw-redirect" title="Web Framework">Web frameworks</a> may provide methods for parsing multiple parameters in the query string, separated by some delimiter.<a href="#cite_note-w3c-recom-3">[3]</a> In the example URL below, multiple query parameters are separated by the <a href="Ampersand" title="Ampersand">ampersand</a>, "<code>&</code>":

<blockquote class="templatequote"><code>https://example.com/path/to/page?name=ferret&color=purple</code></blockquote>

The exact structure of the query string is not standardized. Methods used to parse the query string may differ between websites.

A link in a web page may have a URL that contains a query string. <a href="HTML" title="HTML">HTML</a> defines three ways a user agent can generate the query string:

<ul><li>an <a href="Form_(HTML)" class="mw-redirect" title="Form (HTML)">HTML form</a> via the <code class="nowrap" style=""><form>...</form></code> element</li>

<li>a <a href="Image_map#Server-side" title="Image map">server-side image map</a> via the <code class="mw-highlight mw-highlight-lang-text mw-content-ltr" style="" dir="ltr">ismap</code> attribute on the <code class="nowrap" style=""><img></code> element with an <code class="nowrap" style=""><img ismap></code> construction</li>

<li>an indexed search via the now deprecated <code class="nowrap" style=""><isindex></code> element</li></ul>

<div class="mw-heading mw-heading3"><h3 id="Web_forms">Web forms</h3></div>

One of the original uses was to contain the content of an <a href="Form_(HTML)" class="mw-redirect" title="Form (HTML)">HTML form</a>, also known as web form. In particular, when a form containing the fields <code>field1</code>, <code>field2</code>, <code>field3</code> is submitted, the content of the fields is encoded as a query string as follows:

<blockquote class="templatequote"><code>field1=value1&field2=value2&field3=value3...</code></blockquote>

<ul><li>The query string is composed of a series of field-value pairs.</li>

<li>Within each pair, the field name and value are separated by an <a href="Equals_sign" title="Equals sign">equals sign</a>, "<code>=</code>".</li>

<li>The series of pairs is separated by the <a href="Ampersand" title="Ampersand">ampersand</a>, "<code>&</code>" (<a href="Semicolons" class="mw-redirect" title="Semicolons">semicolons</a> "<code>;</code>" are not recommended by the <a href="W3C" class="mw-redirect" title="W3C">W3C</a> anymore, see below).</li></ul>

While there is no definitive standard, most <a href="Web_framework" title="Web framework">web frameworks</a> allow multiple values to be associated with a single field (e.g. <code>field1=value1&field1=value2&field2=value3</code>).<a href="#cite_note-4">[4]</a><a href="#cite_note-5">[5]</a>

For each <a href="Field_(computer_science)" title="Field (computer science)">field</a> of the form, the query string contains a pair <code><var>field</var>=<var>value</var></code>. Web forms may include fields that are not visible to the user; these fields are included in the query string when the form is submitted.

This convention is a <a href="W3C" class="mw-redirect" title="W3C">W3C</a> recommendation.<a href="#cite_note-w3c-recom-3">[3]</a> In the recommendations of 1999, W3C recommended that all web servers support <a href="Semicolon" title="Semicolon">semicolon</a> separators in addition to <a href="Ampersand" title="Ampersand">ampersand</a> separators<a href="#cite_note-6">[6]</a> to allow <a href="Application/x-www-form-urlencoded" class="mw-redirect" title="Application/x-www-form-urlencoded">application/x-www-form-urlencoded</a> query strings in URLs within HTML documents without having to entity escape ampersands. Since 2014, W3C recommends to use only <a href="Ampersand" title="Ampersand">ampersand</a> as query separator.<a href="#cite_note-w3c-recom-2014-7">[7]</a>

The form content is only encoded in the URL's query string when the form submission method is <a href="GET_(HTTP)" class="mw-redirect" title="GET (HTTP)">GET</a>. The same encoding is used by default when the submission method is <a href="POST_(HTTP)" title="POST (HTTP)">POST</a>, but the result is submitted as the <a href="HTTP_request" class="mw-redirect" title="HTTP request">HTTP request</a> body rather than being included in a modified URL.<a href="#cite_note-html5-8">[8]</a>

<div class="mw-heading mw-heading3"><h3 id="Indexed_search">Indexed search</h3></div>

Before <a href="Form_(HTML)" class="mw-redirect" title="Form (HTML)">forms</a> were added to HTML, browsers rendered the –<code class="nowrap" style=""><isindex></code> element as a single-line text-input control. The text entered into this control was sent to the server as a query string addition to a <a href="GET_(HTTP)" class="mw-redirect" title="GET (HTTP)">GET</a> request for the base URL or another URL specified by the <code class="mw-highlight mw-highlight-lang-text mw-content-ltr" style="" dir="ltr">action</code> attribute.<a href="#cite_note-9">[9]</a> This was intended to allow web servers to use the provided text as query criteria so they could return a list of matching pages.<a href="#cite_note-10">[10]</a>

When the text input into the indexed search control is submitted, it is encoded as a query string as follows:

<blockquote class="templatequote"><code>argument1+argument2+argument3...</code></blockquote>

<ul><li>The query string is composed of a series of arguments by parsing the text into words at the spaces.</li>

<li>The series is separated by the <a href="Plus_sign" class="mw-redirect" title="Plus sign">plus sign</a>, '<code>+</code>'.</li></ul>

Though the <code class="nowrap" style=""><isindex></code> element is deprecated and most browsers no longer support or render it, there are still some vestiges of indexed search in existence. For example, this is the source of the special handling of <a href="Plus_sign" class="mw-redirect" title="Plus sign">plus sign</a>, '<code>+</code>' within browser URL percent encoding (which today, with the deprecation of indexed search, is all but redundant with <code>%20</code>). Also some web servers supporting <a href="Common_Gateway_Interface" title="Common Gateway Interface">CGI</a> (e.g., <a href="Apache_HTTP_Server" title="Apache HTTP Server">Apache</a>) will process the query string into command line arguments if it does not contain an <a href="Equals_sign" title="Equals sign">equals sign</a>, '<code>=</code>' (as per section 4.4 of CGI 1.1). Some CGI scripts still depend on and use this historic behavior for URLs embedded in HTML.

<div class="mw-heading mw-heading2"><h2 id="URL_encoding">URL encoding</h2></div>

/* start https://en.wikipedia.org/ */

.mw-parser-output .hatnote{font-style:italic}.mw-parser-output div.hatnote{padding-left:1.6em;margin-bottom:0.5em}.mw-parser-output .hatnote i{font-style:normal}.mw-parser-output .hatnote+link+.hatnote{margin-top:-0.5em}@media print{body.ns-0 .mw-parser-output .hatnote{display:none!important}}

/* end https://en.wikipedia.org/ */

</style><div role="note" class="hatnote navigation-not-searchable">Main article: <a href="Percent-encoding" title="Percent-encoding">Percent-encoding</a></div>

Some <a href="Character_(computing)" title="Character (computing)">characters</a> cannot be part of a URL (for example, the space) and some other characters have a special meaning in a URL: for example, the character <code>#</code> can be used to further specify a subsection (or <a href="Fragment_identifier" class="mw-redirect" title="Fragment identifier">fragment</a>) of a document. In HTML forms, the character <code>=</code> is used to separate a name from a value. The URI generic syntax uses <a href="Percent-encoding#Percent-encoding_reserved_characters" title="Percent-encoding">URL encoding</a> to deal with this problem, while HTML forms make some additional substitutions rather than applying percent encoding for all such characters. SPACE is encoded as '<code>+</code>' or "<code>%20</code>".<a href="#cite_note-w3schools-11">[11]</a>

<a href="HTML_5" class="mw-redirect" title="HTML 5">HTML 5</a> specifies the following transformation for submitting HTML forms with the "GET" method to a web server. The following is a brief summary of the algorithm:

<ul><li>Characters that cannot be converted to the correct charset are replaced with HTML <a href="Numeric_character_reference" title="Numeric character reference">numeric character references</a><a href="#cite_note-html5_urlencoded-12">[12]</a></li>

<li>SPACE is encoded as '<code>+</code>' or '<code>%20</code>'</li>

<li>Letters (<code>A</code>–<code>Z</code> and <code>a</code>–<code>z</code>), numbers (<code>0</code>–<code>9</code>) and the characters '<code>~</code>','<code>-</code>','<code>.</code>' and '<code>_</code>' are left as-is</li>

<li><code>+</code> is encoded by %2B</li>

<li>All other characters are encoded as a <code>%HH</code> <a href="Hexadecimal" title="Hexadecimal">hexadecimal</a> representation with any non-ASCII characters first encoded as UTF-8 (or other specified encoding)</li></ul>

The octet corresponding to the tilde ("<code>~</code>") is permitted in query strings by RFC3986 but required to be percent-encoded in HTML forms to "<code>%7E</code>".

The encoding of SPACE as '<code>+</code>' and the selection of "as-is" characters distinguishes this encoding from RFC 3986.

<div class="mw-heading mw-heading2"><h2 id="Example">Example</h2></div>

If a <a href="Form_(web)" class="mw-redirect" title="Form (web)">form</a> is embedded in an <a href="HTML" title="HTML">HTML</a> page as follows:

</form>

</pre></div>

and the user inserts the strings "this is a field" and "was it clear (already)?" in the two <a href="Text_box" title="Text box">text fields</a> and presses the submit button, the program <code>test.cgi</code> (the program specified by the <code>action</code> <a href="HTML_attribute" title="HTML attribute">attribute</a> of the <code>form</code> <a href="HTML_element" title="HTML element">element</a> in the above example) will receive the following query string:

<code>first=this+is+a+field&second=was+it+clear+%28already%29%3F</code>.

If the form is processed on the <a href="Web_server" title="Web server">server</a> by a <a href="Common_Gateway_Interface" title="Common Gateway Interface">CGI</a> <a href="Scripting_language" title="Scripting language">script</a>, the script may typically receive the query string as an <a href="Environment_variable" title="Environment variable">environment variable</a> named <code>QUERY_STRING</code>.

<div class="mw-heading mw-heading2"><h2 id="Tracking">Tracking</h2></div>

A program receiving a query string can ignore part or all of it. If the requested URL corresponds to a file and not to a program, the whole query string is ignored. However, regardless of whether the query string is used or not, the whole URL including it is stored in the server <a href="Computer_data_logging" class="mw-redirect" title="Computer data logging">log files</a>.

These facts allow query strings to be used to track users in a manner similar to that provided by <a href="HTTP_cookie" title="HTTP cookie">HTTP cookies</a>. For this to work, every time the user downloads a page, a unique identifier must be chosen and added as a query string to the URLs of all links the page contains. As soon as the user follows one of these links, the corresponding URL is requested to the server. This way, the download of this page is linked with the previous one.

For example, when a web page containing the following is requested:

<a href="bar.html">mine is better</a>

</pre></div>

a unique string, such as <code>e0a72cb2a2c7</code> is chosen, and the page is modified as follows:

<a href="bar.html?e0a72cb2a2c7">mine is better</a>

</pre></div>

The addition of the query string does not change the way the page is shown to the user. When the user follows, for example, the first link, the browser requests the page <code>foo.html?e0a72cb2a2c7</code> to the server, which ignores what follows <code>?</code> and sends the page <code>foo.html</code> as expected, adding the query string to its links as well.

This way, any subsequent page request from this user will carry the same query string <code>e0a72cb2a2c7</code>, making it possible to establish that all these pages have been viewed by the same user. Query strings are often used in association with <a href="Web_beacon" title="Web beacon">web beacons</a>.

The main differences between query strings used for tracking and HTTP cookies are that:

<ol><li>Query strings form part of the URL, and are therefore included if the user saves or sends the URL to another user; cookies can be maintained across browsing sessions, but are not saved or sent with the URL.</li>

<li>If the user arrives at the same web server by two (or more) independent paths, it will be assigned two different query strings, while the stored cookies are the same.</li>

<li>The user can disable cookies, in which case using cookies for tracking does not work. However, using query strings for tracking should work in all situations.</li>

<li>Different query strings passed by different visits to the page will mean that the pages are never served from the browser (or proxy, if present) cache thereby increasing the load on the web server and slowing down the user experience.</li></ol>

<div class="mw-heading mw-heading2"><h2 id="Compatibility_issues">Compatibility issues</h2></div>

According to the <a href="Hypertext_Transfer_Protocol" class="mw-redirect" title="Hypertext Transfer Protocol">HTTP</a> specification:

<blockquote>Various ad hoc limitations on request-line length are found in practice. It is RECOMMENDED that all HTTP senders and recipients support, at a minimum, request-line lengths of 8000 octets.<a href="#cite_note-13">[13]</a></blockquote>

If the URL is too long, the web server fails with the <a href="List_of_HTTP_status_codes#414" title="List of HTTP status codes">414 Request-URI Too Long</a> HTTP status code.

The common workaround for these problems is to use <a href="POST_(HTTP)" title="POST (HTTP)">POST</a> instead of <a href="GET_(HTTP)" class="mw-redirect" title="GET (HTTP)">GET</a> and store the parameters in the request body. The length limits on request bodies are typically much higher than those on URL length. For example, the limit on POST size, by default, is 2 MB on IIS 4.0 and 128 KB on IIS 5.0. The limit is configurable on Apache2 using the <code>LimitRequestBody</code> directive, which specifies the number of bytes from 0 (meaning unlimited) to 2147483647 (2 GB) that are allowed in a request body.<a href="#cite_note-14">[14]</a>

/* start https://en.wikipedia.org/ */

.mw-parser-output .div-col{margin-top:0.3em;column-width:30em}.mw-parser-output .div-col-small{font-size:90%}.mw-parser-output .div-col-rules{column-rule:1px solid #aaa}.mw-parser-output .div-col dl,.mw-parser-output .div-col ol,.mw-parser-output .div-col ul{margin-top:0}.mw-parser-output .div-col li,.mw-parser-output .div-col dd{page-break-inside:avoid;break-inside:avoid-column}

/* end https://en.wikipedia.org/ */

</style><div class="div-col">

<ul><li><a href="Clean_URL" title="Clean URL">Clean URL</a></li>

<li><a href="DoubleClick_Click_Identifier" class="mw-redirect" title="DoubleClick Click Identifier">Click identifier</a></li>

<li><a href="Common_Gateway_Interface" title="Common Gateway Interface">Common Gateway Interface</a> (CGI)</li>

<li><a href="HTTP_cookie" title="HTTP cookie">HTTP cookie</a></li>

<li><a href="HyperText_Transfer_Protocol" class="mw-redirect" title="HyperText Transfer Protocol">HyperText Transfer Protocol</a> (HTTP)</li>

<li><a href="Semantic_URL" class="mw-redirect" title="Semantic URL">Semantic URLs</a></li>

<li><a href="URI_fragment" title="URI fragment">URI fragment</a></li>

<li><a href="URI_normalization" title="URI normalization">URI normalization</a></li>

<li><a href="URI_scheme" class="mw-redirect" title="URI scheme">URI scheme</a></li>

<li><a href="UTM_parameters" title="UTM parameters">UTM parameters</a></li>

<li><a href="Web_beacon" title="Web beacon">Web beacon</a></li></ul>

</div>

<div class="mw-heading mw-heading2"><h2 id="References">References</h2></div>

/* start https://en.wikipedia.org/ */

.mw-parser-output .reflist{margin-bottom:0.5em;list-style-type:decimal}@media screen{.mw-parser-output .reflist{font-size:90%}}.mw-parser-output .reflist .references{font-size:100%;margin-bottom:0;list-style-type:inherit}.mw-parser-output .reflist-columns-2{column-width:30em}.mw-parser-output .reflist-columns-3{column-width:25em}.mw-parser-output .reflist-columns{margin-top:0.3em}.mw-parser-output .reflist-columns ol{margin-top:0}.mw-parser-output .reflist-columns li{page-break-inside:avoid;break-inside:avoid-column}.mw-parser-output .reflist-upper-alpha{list-style-type:upper-alpha}.mw-parser-output .reflist-upper-roman{list-style-type:upper-roman}.mw-parser-output .reflist-lower-alpha{list-style-type:lower-alpha}.mw-parser-output .reflist-lower-greek{list-style-type:lower-greek}.mw-parser-output .reflist-lower-roman{list-style-type:lower-roman}

/* end https://en.wikipedia.org/ */

</style><div class="reflist">

/* start https://en.wikipedia.org/ */

.mw-parser-output cite.citation{font-style:inherit;word-wrap:break-word}.mw-parser-output .citation q{quotes:"\"""\"""'""'"}.mw-parser-output .citation:target{background-color:rgba(0,127,255,0.133)}.mw-parser-output .id-lock-free.id-lock-free a{background:url("./mw/Lock-green.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-limited.id-lock-limited a,.mw-parser-output .id-lock-registration.id-lock-registration a{background:url("./mw/Lock-gray-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-subscription.id-lock-subscription a{background:url("./mw/Lock-red-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .cs1-ws-icon a{background:url("./mw/Wikisource-logo.svg")right 0.1em center/12px no-repeat}body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-free a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-limited a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-registration a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-subscription a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .cs1-ws-icon a{background-size:contain;padding:0 1em 0 0}.mw-parser-output .cs1-code{color:inherit;background:inherit;border:none;padding:inherit}.mw-parser-output .cs1-hidden-error{display:none;color:var(--color-error,#d33)}.mw-parser-output .cs1-visible-error{color:var(--color-error,#d33)}.mw-parser-output .cs1-maint{display:none;color:#085;margin-left:0.3em}.mw-parser-output .cs1-kern-left{padding-left:0.2em}.mw-parser-output .cs1-kern-right{padding-right:0.2em}.mw-parser-output .citation .mw-selflink{font-weight:inherit}@media screen{.mw-parser-output .cs1-format{font-size:95%}html.skin-theme-clientpref-night .mw-parser-output .cs1-maint{color:#18911f}}@media screen and (prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .cs1-maint{color:#18911f}}

/* end https://en.wikipedia.org/ */

</style><cite id="CITEREFT._Berners-LeeR._FieldingL._Masinter2005" class="citation web cs1">T. Berners-Lee; R. Fielding; L. Masinter (January 2005). <a rel="nofollow" class="external text" href="http://tools.ietf.org/html/rfc3986#section-3">"RFC 3986"</a>. "Syntax Components" (section 3).</cite>

</li>

<li id="cite_note-2"><a href="#cite_ref-2">^</a> <cite id="CITEREFT._Berners-LeeR._FieldingL._Masinter2005" class="citation web cs1">T. Berners-Lee; R. Fielding; L. Masinter (January 2005). <a rel="nofollow" class="external text" href="http://tools.ietf.org/html/rfc3986#section-3.4">"RFC 3986"</a>. "Query" (section 3.4).</cite>

</li>

<li id="cite_note-w3c-recom-3">^ <a href="#cite_ref-w3c-recom_3-0">a</a> <a href="#cite_ref-w3c-recom_3-1">b</a> <a rel="nofollow" class="external text" href="https://www.w3.org/TR/REC-html40/interact/forms.html#form-content-type">Forms in HTML documents</a>. W3.org. Retrieved on 2013-09-08.

</li>

<li id="cite_note-4"><a href="#cite_ref-4">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://docs.oracle.com/javaee/6/api/javax/servlet/ServletRequest.html#getParameterValues(java.lang.String)">"ServletRequest (Java EE 6 )"</a>. docs.oracle.com. 2011-02-10. Retrieved 2013-09-08.</cite>

</li>

<li id="cite_note-5"><a href="#cite_ref-5">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://stackoverflow.com/questions/1746507/authoritative-position-of-duplicate-http-get-query-keys">"uri – Authoritative position of duplicate HTTP GET query keys"</a>. Stack Overflow. 2013-06-09. Retrieved 2013-09-08.</cite>

</li>

<li id="cite_note-6"><a href="#cite_ref-6">^</a> <a rel="nofollow" class="external text" href="http://www.w3.org/TR/1999/REC-html401-19991224/appendix/notes.html#h-B.2.2">Performance, Implementation, and Design Notes</a>. W3.org. Retrieved on 2013-09-08.

</li>

<li id="cite_note-w3c-recom-2014-7"><a href="#cite_ref-w3c-recom-2014_7-0">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://www.w3.org/TR/2014/REC-html5-20141028/forms.html#url-encoded-form-data">"4.10 Forms — HTML5"</a>.</cite>

</li>

<li id="cite_note-html5-8"><a href="#cite_ref-html5_8-0">^</a> <a rel="nofollow" class="external autonumber" href="https://www.w3.org/TR/html52/sec-forms.html#form-submission-algorithm">[1]</a>, HTML5.2, W3C recommendation, 14 December 2017

</li>

<li id="cite_note-9"><a href="#cite_ref-9">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://web.archive.org/web/20171019030835/https://developer.mozilla.org/en-US/docs/Web/HTML/Element/isindex">"<isindex>"</a>. HTML (HyperText Markup Language). Archived from <a rel="nofollow" class="external text" href="https://developer.mozilla.org/en-US/docs/Web/HTML/Element/isindex">the original</a> on 2017-10-19. Retrieved 2015-11-21.</cite>

</li>

<li id="cite_note-10"><a href="#cite_ref-10">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://web.archive.org/web/20210622024419/https://www.w3.org/wiki/HTML/Elements/isindex">"HTML/Elements/isindex"</a>. W3C Wiki. Archived from <a rel="nofollow" class="external text" href="https://www.w3.org/wiki/HTML/Elements/isindex">the original</a> on 2021-06-22. Retrieved 2020-03-20.</cite>

</li>

<li id="cite_note-w3schools-11"><a href="#cite_ref-w3schools_11-0">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://www.w3schools.com/tags/ref_urlencode.asp">"HTML URL Encoding Reference"</a>. W3Schools. Retrieved May 1, 2013.</cite>

</li>

<li id="cite_note-html5_urlencoded-12"><a href="#cite_ref-html5_urlencoded_12-0">^</a> The <a rel="nofollow" class="external text" href="https://www.w3.org/TR/html52/sec-forms.html#application-x-www-form-urlencoded-encoding-algorithm">application/x-www-form-urlencoded encoding algorithm</a>, HTML5.2, W3C recommendation, 14 December 2017

</li>

<li id="cite_note-13"><a href="#cite_ref-13">^</a> <a rel="nofollow" class="external text" href="https://tools.ietf.org/html/rfc7230#section-3.1.1">HTTP/1.1 Message Syntax and Routing</a>. ietf.org. Retrieved on 2014-07-31.

</li>

<li id="cite_note-14"><a href="#cite_ref-14">^</a> <a rel="nofollow" class="external text" href="https://httpd.apache.org/docs/2.2/mod/core.html#limitrequestbody">core – Apache HTTP Server</a>. Httpd.apache.org. Retrieved on 2013-09-08.

</li>

</ol></div></div></div><div><div class="zim-footer">

This article is issued from <a class="external text" title="Last edited on 2025-07-14" href="https://en.wikipedia.org/wiki/?title=Query_string&oldid=1300456904">Wikipedia</a>. The text is available under <a class="external text" href="https://creativecommons.org/licenses/by-sa/4.0/deed.en">Creative Commons Attribution-Share Alike 4.0</a> unless otherwise noted. Additional terms may apply for the media files.

</div>

</div></div>

</div>

</main>

</div>

</body></html>